Solana Colosseum hackathon · University of Exeter
Construkt
I led product and project delivery for a five-person team building a Solana-backed construction payment MVP. We interviewed construction professionals, scoped the product around their payment and approval problems, then delivered a working submission with a demo and pitch.
Challenge
Put payment decisions and project evidence on one path
Construction professionals described payment agreements buried in email threads, teams working from different document versions and delays around sign-off. Contractors and clients then struggle to agree on completed work, approved changes and the payment due.
Our team used those interviews to define the product problem. We designed Construkt to connect milestones, approvals, variations and payment release in one shared record, with Solana escrow enforcing the release conditions.
MVP question: Could both sides follow the same project history and release escrowed funds after both had approved the agreed conditions?
My contribution
I took the project from research to a coordinated build
I built the team across frontend, backend and business development, then kept those workstreams aligned through the hackathon. My product work covered the interviews, MVP scope, role-based dashboards and escrow workflow.
Validate the problem
I interviewed construction professionals and turned their payment and approval problems into product requirements.
Set the MVP boundary
I focused the build on shared milestones, role-based actions, escrow release and a traceable project record.
Coordinate delivery
I kept the frontend, backend and business work aligned around the same end-to-end flow.
Prepare the submission
I brought the team’s product work into the Colosseum demo and sales pitch.
Product design
Two roles, one approval record
I designed separate dashboard views for contractors and clients because each side needed different controls. I based both views on the same milestones, variations and payment history, then worked with the team to support that flow across the interface and backend.
The Solana program held funds in escrow until the contractor and client approved the agreed conditions. After approval, the program released the payment and kept the transaction in the project record.
Agree milestones
The contractor and client work from the same project stages and terms.
Fund escrow
The client places project funds in Solana escrow under the agreed release rules.
Approve the work
Each user sees the status and actions needed to confirm an agreed milestone.
Release and record
The program releases funds after approval and retains the payment trail on chain.
Commercial model: The team framed Construkt as B2B software with a subscription tied to project size and a fee when escrow released.
Outcome
A working MVP, product demo and hackathon pitch
The five-person team completed an end-to-end MVP for the Solana Colosseum hackathon. We joined the role-based web interface, Solana escrow rules and business case into one product story.
I worked between discovery and delivery: choosing the problem with industry input, setting the product boundary and keeping three workstreams focused on the same release flow.
Product demo
Hackathon sales pitch
Construkt grew from our earlier smart contracts coursework. View SmartFundX